Skip to content

[docs] Add comments / instructions about the new database migrations#4733

Draft
junaway wants to merge 1 commit into
mainfrom
docs/improve-internal-docs-about-database-migrations
Draft

[docs] Add comments / instructions about the new database migrations#4733
junaway wants to merge 1 commit into
mainfrom
docs/improve-internal-docs-about-database-migrations

Conversation

@junaway

@junaway junaway commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI review requested due to automatic review settings June 18, 2026 14:40
@vercel

vercel Bot commented Jun 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agenta-documentation Ready Ready Preview, Comment Jun 18, 2026 2:40pm

Request Review

@dosubot dosubot Bot added size:M This PR changes 30-99 lines, ignoring generated files. documentation Improvements or additions to documentation labels Jun 18, 2026
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 035a6f83-894d-4af0-af94-f8d7e8dadac4

📥 Commits

Reviewing files that changed from the base of the PR and between a97e608 and 6f3cd03.

📒 Files selected for processing (5)
  • api/AGENTS.md
  • api/ee/databases/postgres/migrations/core/README.md
  • api/ee/databases/postgres/migrations/tracing/README.md
  • api/oss/databases/postgres/migrations/core/README.md
  • api/oss/databases/postgres/migrations/tracing/README.md

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated migration chain documentation across development and production configurations to clarify status of active and legacy migration paths.
    • Added guidance directing new database schema changes to designated active migration chains and specifying shared versus edition-specific change locations.

Walkthrough

Five documentation files are updated to declare the legacy core/ and tracing/ Alembic migration chains frozen at park00000000. Four migration chain READMEs gain IMPORTANT banners redirecting contributors to the active core_oss/, core_ee/, tracing_oss/, and tracing_ee/ chains. api/AGENTS.md gains a new subsection consolidating the same routing rules.

Changes

Parked Migration Chain Documentation

Layer / File(s) Summary
Parked-chain notices in migration READMEs
api/oss/databases/postgres/migrations/core/README.md, api/oss/databases/postgres/migrations/tracing/README.md, api/ee/databases/postgres/migrations/core/README.md, api/ee/databases/postgres/migrations/tracing/README.md
Each README receives an IMPORTANT block declaring its chain frozen, forbidding new revisions, and providing a scope-to-active-chain mapping table (including version tables and OSS/EE applicability) along with correct alembic revision working-directory instructions.
AGENTS.md migration chain guidance
api/AGENTS.md
Adds a "Database schema migrations (which alembic chain)" subsection referencing the parked chains, specifying where to place shared vs EE-only revisions, and linking to the design doc and parked core/README.md.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No pull request description was provided by the author, making it impossible to assess relevance to the changeset. Add a brief description explaining the purpose of these migration documentation updates and which changes warrant the restructuring.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: adding documentation and instructions about database migrations across multiple README files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/improve-internal-docs-about-database-migrations

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds prominent documentation banners and contributor guidance to prevent new Alembic revisions from being created in the legacy parked core/ and tracing/ migration chains, and to direct authors to the active OSS/EE split chains instead.

Changes:

  • Adds [!IMPORTANT] “parked chain” warnings to OSS and EE core/ and tracing/ migration READMEs.
  • Documents the active chain matrix (OSS/EE, core/tracing, version tables, roots) in the OSS core/ README.
  • Adds contributor instructions in api/AGENTS.md on which chain to use for shared vs EE-only schema changes.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
api/oss/databases/postgres/migrations/tracing/README.md Adds parked-chain warning and directs new tracing migrations to tracing_oss/ / tracing_ee/.
api/oss/databases/postgres/migrations/core/README.md Adds parked-chain warning plus an active-chain matrix and guidance for authoring in core_oss/ / core_ee/.
api/ee/databases/postgres/migrations/tracing/README.md Adds parked-chain warning for EE tracing legacy chain and points to active chains.
api/ee/databases/postgres/migrations/core/README.md Adds parked-chain warning for EE core legacy chain and points to active chains.
api/AGENTS.md Adds contributor guidance on selecting the correct Alembic chain for new schema migrations.
Comments suppressed due to low confidence (1)

api/ee/databases/postgres/migrations/tracing/README.md:7

  • The banner says tracing/ is parked, but the Making migrations command below runs with -w .../migrations/core (wrong directory) and would create a revision in the parked chain. It should point at the active tracing_oss/ (shared) or tracing_ee/ (EE-only) chain instead.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +22 to +23
> The commands below still describe the alembic mechanics, but swap the `-w .../core`
> working directory for `.../core_oss` (or the right active chain) when creating revisions.
Comment on lines +22 to +23
> The commands below still describe the alembic mechanics, but swap the `-w .../core`
> working directory for `.../core_oss` (or the right active chain) when creating revisions.
Comment on lines +4 to +8
> **This `tracing/` chain is PARKED (frozen legacy history).** Do **not** add new
> revisions here — it ends at `park00000000` and never advances. Author new tracing
> migrations in `tracing_oss/` (shared, runs in both editions) or `tracing_ee/` (EE-only).
> See the parked `core/README.md` banner and
> `docs/designs/oss-ee-convergence/migration-chains-and-edition-switch.md`.
Comment on lines +4 to +8
> **This `tracing/` chain is PARKED (frozen legacy history).** Do **not** add new
> revisions here — it ends at `park00000000` and never advances. Author new tracing
> migrations in `tracing_oss/` (shared, runs in both editions) or `tracing_ee/` (EE-only).
> See the parked `core/README.md` banner and
> `docs/designs/oss-ee-convergence/migration-chains-and-edition-switch.md`.
Comment on lines +4 to +8
> **This `core/` chain is PARKED (frozen legacy history).** Do **not** add new revisions
> here — it ends at `park00000000` and never advances. Shared schema changes go in
> `oss/databases/postgres/migrations/core_oss/` (EE ships and runs the `oss/` tree);
> EE-only schema goes in `core_ee/`. Full rules:
> `docs/designs/oss-ee-convergence/migration-chains-and-edition-switch.md`.
Comment on lines +4 to +8
> **This `core/` chain is PARKED (frozen legacy history).** Do **not** add new revisions
> here — it ends at `park00000000` and never advances. Shared schema changes go in
> `oss/databases/postgres/migrations/core_oss/` (EE ships and runs the `oss/` tree);
> EE-only schema goes in `core_ee/`. Full rules:
> `docs/designs/oss-ee-convergence/migration-chains-and-edition-switch.md`.
Comment thread api/AGENTS.md
Comment on lines +91 to +93
Full model (version tables, fresh-install/upgrade/OSS→EE-switch flows, FK and replay-skew
rules): `docs/designs/oss-ee-convergence/migration-chains-and-edition-switch.md`. The
parked `core/README.md` covers alembic mechanics.
@github-actions

github-actions Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Railway Preview Environment

Status Destroyed (PR converted to draft)

Updated at 2026-06-18T16:45:05.556Z

@junaway junaway marked this pull request as draft June 18, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants